FIX select on ticket list for fields group and severity (issue #31619) #32122
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thomas-Ngr
force-pushed
the
20.0_fix_search_select_ticket_list
branch
2 times, most recently
from
5f32ace
to
b82111c
Compare
thomas-Ngr
force-pushed
the
20.0_fix_search_select_ticket_list
branch
from
b82111c
to
f68bf4f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FIX select group and severity search fields on ticket list
issue #31619 (indicates 20.0, but I encountered it also on develop)
see also PR #32120 , which is similar but for ticket type, and brings more details.
group and severity must be set when creating/updating a ticket, and have a default value.
However, on search fields, we don't want to set the default value.
This PR sets the default value only if
$emptyis not set.These are the changes brought by this PR :
if no default value :
